In the identity view there are fields for entering the 窶廸ame窶, 窶廚ode窶 and 窶弑nit窶 attributes of an event.
The 窶廸ame窶 attribute obviously contains the name of the event. Since this is usually the attribute shown in the title field of the event, you should select a name that makes it easy for you to identify which message the event sends. Apart from that there are no special rules.
The 窶廚ode窶 attribute can be used as a supplement to the 窶廸ame窶 attribute to further help you identify the message. Again you are free to apply any coding system you like, or just ignore this field if you do not need it.
Note, however, that if you do not want to bother entering the code yourself, you can use the 窶彗utocode窶 feature. This option is controlled by using the 窶廸odes and events窶ｦ窶 command in the 窶弃reference窶 submenu of the 窶廡ile窶 menu. If the 窶廣uto code窶 option is checked, DynRisk will generate a code for you based on the code of the parent folder and the number of objects in this folder. In particular if you create a new event inside a folder with code 窶廣窶 and this event is the sixth object in this folder, the auto code for this event would be 窶廣.06窶.
In the 窶弑nit窶 field you specify the unit of the event. Since events cannot be stored on file during a simulation, the 窶弑nit窶 attribute is less important for events than it is for nodes. However, entering a correct unit for each event, still makes your model easier to understand.
Note that if you are working on a model where all or most of the events have the same unit, you can save a lot of work by entering this unit as the default unit. This is done by using the 窶廸odes and events窶ｦ窶 command in the 窶弃reference窶 submenu of the 窶廡ile窶 menu.
The 窶廳ind窶 attribute, controlled by the corresponding popup menu is another optional identifier. Just as for nodes, DynRisk lets you choose between the following predefined kinds:
窶｢ General
窶｢ Boolean
窶｢ Category
窶｢ Constraint
窶｢ Cost
窶｢ Count
窶｢ Date
窶｢ Decision
窶｢ Duration
窶｢ Length
窶｢ Manhrs.
窶｢ Price
窶｢ Rate
窶｢ Volume
窶｢ Weight
窶｢ User 1
窶｢ User 2
窶｢ User 3
窶｢ User 4
If you do not need this attribute, just use 窶廨eneral窶 as kind. If you do not find anything appropriate, use 窶弑ser 1窶, 窶弑ser 2窶, 窶弑ser 3窶 or 窶弑ser 4窶, and replace this by something more suitable in your final risk analysis report.
Note that if you are working on a model where all or most of the events have the same kind, you can save a lot of work by selecting this kind as the default kind. This is done by using the 窶廸odes and events窶ｦ窶 command in the 窶弃reference窶 submenu of the 窶廡ile窶 menu.
In addition to the attributes we have mentioned so far, the 窶廬dentity窶 view contains two more:
窶｢ Creation date
窶｢ Revision date
The creation date shows the date when the event was created, while the revision date shows the date for the last saved changes. If the model has not been saved on file since the event was created, you will only see a dash instead of a revision date.
For obvious reasons, the creation and revision dates cannot be edited.
